✅ Deploy Preview for cerulean-figolla-1f9435 ready!

Name	Link
🔨 Latest commit	7a718fc
🔍 Latest deploy log	https://app.netlify.com/projects/cerulean-figolla-1f9435/deploys/699517cd2302d50008162db8
😎 Deploy Preview	https://deploy-preview-8222--cerulean-figolla-1f9435.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Codecov Report

❌ Patch coverage is 83.33333% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.57%. Comparing base (e56785c) to head (7a718fc).

@@            Coverage Diff             @@
##             main    #8222      +/-   ##
==========================================
- Coverage   73.57%   73.57%   -0.01%     
==========================================
  Files         242      242              
  Lines       37000    37004       +4     
==========================================
+ Hits        27224    27225       +1     
- Misses       7854     7856       +2     
- Partials     1922     1923       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

what will be the cluster name for the non backend filter case when there are N backendRefs

what will be the cluster name for the non backend filter case when there are N backendRefs

change from httproute/default/httproute/rule/0 to httproute/default/httproute/rule/0/backend/0

what does the 0 in backend/0 map to if there are N backends

what does the 0 in backend/0 map to if there are N backends

Nothing

If need N clusters, you will got backend/1.

what does the 0 in backend/0 map to if there are N backends

Nothing

If need N clusters, you will got backend/1.

can you elaborate what xDS resources will be needed

• route
• weighted cluster
• cluster

today, for this case, we dont use any weighted cluster for this case

for this case

  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /login
    backendRefs:
    - name: foo-svc-1
      port: 8080
     - name: foo-svc-2
      port: 8080
     - name: foo-svc-3
      port: 8080

what does the 0 in backend/0 map to if there are N backends

Nothing
If need N clusters, you will got backend/1.

can you elaborate what xDS resources will be needed

• route
• weighted cluster
• cluster

today, for this case, we dont use any weighted cluster for this case

for this case

  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /login
    backendRefs:
    - name: foo-svc-1
      port: 8080
     - name: foo-svc-2
      port: 8080
     - name: foo-svc-3
      port: 8080

yeah, today you will have a cluster named httproute/ns/name/rule/0.
After you add filters to the backend, you will got three new clusters:

• httproute/ns/name/rule/0/backend/0
• httproute/ns/name/rule/0/backend/1
• httproute/ns/name/rule/0/backend/2

With this patch, httproute/ns/name/rule/0/backend/0 will always there to avoid NC when CP updateing the XDS.

httproute/ns/name/rule/0/backend/0

-1 on special naming only for 0th index

the field name here impacts

• triaging
• tooling ingesting config dump
• metrics

and this will add unnecessary complexity and cognitive load for users

httproute/ns/name/rule/0/backend/0

-1 on special naming only for 0th index

the field name here impacts

• triaging
• tooling ingesting config dump
• metrics

and this will add unnecessary complexity and cognitive load for users

I understand this's an edge case, could we do something to reduce the noise? what about add a runtime flag for this?